Release 10.1A: OpenEdge Development:
Progress Dynamics Managers API Reference

Overview

The Localization Manager supports the run-time translation of all the elements in the context of an application screen. This includes such items as window titles, labels, and messages. This aids your deployment of an application that must run in many different languages.

In a distributed environment, the Localization Manager is started on both the client and server sides. There is a wrapper program for each side that sets the global variable, server-side, to either YES for the server-side version or NO for the client-side version. Both programs then include the main code of the manager from the af\app\aftrnmngrp.i include file. The differences in how the manager operates on each side are triggered by checking the value of the server-side variable.

The Localization Manager’s handle is stored in the global shared variable, gshTranslationManager.

Table 5–1 shows the files that contain the Localization Manager’s code.

Table 5–1: Localization Manager files

Type	Path
Client-side wrapper	af\app\aftrnclntp.p
Server-side wrapper	af\app\aftrnsrvrp.p
Main code	af\app\aftrnmngrp.i
Included files	adm2\tttranslate.i af\app\aftrnbldtrncp.i af\app\aftrngetmtrnp.i af\app\aftrnupdmtrnp.i af\app\aftttranslation.i af\sup2\afcheckerr.i af\sup2\afglobals.i

For more information on this Manager, see the chapter on using the Progress Dynamics Managers in OpenEdge Development: Progress Dynamics Advanced Development .